## Description

Adds `scripts/customer_testing.dart` so that Flame can be registered in
the [flutter/tests
registry](https://github.com/flutter/tests/tree/main/registry).

The registry runs downstream packages' tests as a presubmit against
`flutter/flutter` framework changes, so that breaking changes to the
framework that would affect Flame are caught early (and Flame's code can
be auto-migrated via `dart fix`).

A companion PR is open against `flutter/tests`: flutter/tests#489. It
adds a `registry/flame.test` entry pinned to the commit of this PR that
invokes the script via `dart run scripts/customer_testing.dart`.

## Why a single Dart script

The registry guarantees `dart` on the path, and a single Dart file is
inherently cross-platform, so there's no need for the separate
`.sh`/`.bat` pair the registry template otherwise expects. It also
matches the existing `scripts/test_formatter.dart`.

## Behavior

- Flame is a pub workspace, so the registry's `update` step (`flutter
pub get` at the repo root) resolves every member package.
- `flutter analyze --no-fatal-infos` runs over the whole workspace on
**every platform**.
- The full per-package `flutter test` suites run on **Linux only**,
since golden and rendering tests are platform-sensitive. This mirrors
how `flutter/packages` handles its own registry entry.

Locally verified: root `flutter pub get` resolves the workspace, the
script's analyze pass is clean over the whole tree, and per-package
`flutter test` works.

## What

Adds `scripts/customer_testing.dart`, the entry point invoked by the
[flutter/tests](https://github.com/flutter/tests) registry to run this
repository's tests as a presubmit against `flutter/flutter` framework
changes.

This is the supabase-flutter counterpart of what Flame did in
[flutter/tests#489](flutter/tests#489). A
companion PR to `flutter/tests` adds the
`registry/supabase_flutter.test` entry that clones this repo at a pinned
commit and runs this script.

## What the script does

1. `flutter analyze --no-fatal-infos` over the whole pub workspace
(covers every member package).
2. `flutter test` in `packages/supabase_flutter`.

Only `supabase_flutter` is exercised because it is hermetic (mock/stub
based). The other packages' tests require a live Supabase backend and
are therefore not eligible for the registry, which requires hermetic
tests (no network, no spawned services).

## Why

So that Flutter framework regressions affecting `supabase_flutter` are
caught upstream, before they reach a stable Flutter release.

## Notes

- The registry only honors changes here once the pinned commit in the
flutter/tests entry is updated (revision bumps are periodic PRs to
flutter/tests).
- Verified locally: `dart run scripts/customer_testing.dart` passes
(analyze clean, 57 tests pass).


Part of SDK-1216

Adds a registry entry for [supabase-flutter](https://github.com/supabase/supabase-flutter), the official Supabase client library for Flutter/Dart, so that framework changes are checked against its tests as a presubmit.

Follows the same pattern as the Flame entry (#489): the entry clones supabase-flutter at a pinned commit and runs `scripts/customer_testing.dart`, which:

1. Runs `flutter analyze --no-fatal-infos` over the whole pub workspace (covers every member package).
2. Runs `flutter test` in `packages/supabase_flutter`.

Only `supabase_flutter` is exercised because it is hermetic (mock/stub based). The repo's other packages have tests that require a live Supabase backend, so they are not included here.

The `scripts/customer_testing.dart` script is added in supabase/supabase-flutter#1528.

contact: lukas.klingsbo@supabase.io

This bumps the customer testing commit to pick up tests from 
- flutter/tests#490
- flutter/tests#489

FYI @spydon :)

## Pre-launch Checklist

- [x] I read the [Contributor Guide] and followed the process outlined
there for submitting PRs.
- [x] I read the [AI contribution guidelines] and understand my
responsibilities, or I am not using AI tools.
- [x] I read the [Tree Hygiene] wiki page, which explains my
responsibilities.
- [x] I read and followed the [Flutter Style Guide], including [Features
we expect every widget to implement].
- [x] I signed the [CLA].
- [ ] I listed at least one issue that this PR fixes in the description
above.
- [x] I updated/added relevant documentation (doc comments with `///`).
- [x] I added new tests to check the change I am making, or this PR is
[test-exempt].
- [x] I followed the [breaking change policy] and added [Data Driven
Fixes] where supported.
- [x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel
on [Discord].

If this change needs to override an active code freeze, provide a
comment explaining why. The code freeze workflow can be overridden by
code reviewers. See pinned issues for any active code freezes with
guidance.

**Note**: The Flutter team is currently trialing the use of [Gemini Code
Assist for
GitHub](https://developers.google.com/gemini-code-assist/docs/review-github-code).
Comments from the `gemini-code-assist` bot should not be taken as
authoritative feedback from the Flutter team. If you find its comments
useful you can update your code accordingly, but if you are unsure or
disagree with the feedback, please feel free to wait for a Flutter team
member's review for guidance on which automated comments should be
addressed.

<!-- Links -->
[Contributor Guide]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#overview
[AI contribution guidelines]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#ai-contribution-guidelines
[Tree Hygiene]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md
[test-exempt]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#tests
[Flutter Style Guide]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md
[Features we expect every widget to implement]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md#features-we-expect-every-widget-to-implement
[CLA]: https://cla.developers.google.com/
[flutter/tests]: https://github.com/flutter/tests
[breaking change policy]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#handling-breaking-changes
[Discord]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Chat.md
[Data Driven Fixes]:
https://github.com/flutter/flutter/blob/main/docs/contributing/Data-driven-Fixes.md